Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

asset/metadata: save metadata file in asset state file #1538

Merged
merged 1 commit into from
Apr 5, 2019
Merged

asset/metadata: save metadata file in asset state file #1538

merged 1 commit into from
Apr 5, 2019

Conversation

staebler
Copy link
Contributor

@staebler staebler commented Apr 5, 2019

The Metadata asset uses a private field for its file. This prevents the file from being saved when the asset state file is generated. When create ignition-configs is called prior to create cluster, then Metadata asset does not have a file.

This does not present a problem to the end user yet, because the Metadata asset, as a read-only asset, is not consumed during the call to create cluster.

The Metadata asset uses a private field for its file. This
prevents the file from being saved when the asset state file
is generated. When `create ignition-configs` is called prior
to `create cluster`, then Metadata asset does not have a
file.

This does not present a problem to the end user yet,
because the Metadata asset, as a read-only asset, is not
consumed during the call to `create cluster`.
@openshift-ci-robot openshift-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Apr 5, 2019
@abhinavdahiya
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 5, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, staebler

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [abhinavdahiya,staebler]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit 72b49a3 into openshift:master Apr 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants