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

feat(pkger): add ability to export by stack #18322

Merged
merged 2 commits into from
Jun 2, 2020

Conversation

jsteenb2
Copy link
Contributor

@jsteenb2 jsteenb2 commented Jun 1, 2020

this ability exports all resources associated with a stack by the same
metadata.name fields as the original application had done it. This can
be used as a means to snapshot the current state of the stack. This can
be used for source control or other means.

closes: #18271


Acceptance Criteria

  • exporting a pkg with a stack id exports the pkg using the existing
  • deleted resources, are no exported (there is nothing to export)
  • extend CLI with influx pkg export stack $STACK_ID

  • CHANGELOG.md updated with a link to the PR (not the Issue)
  • Well-formatted commit messages
  • Rebased/mergeable
  • Tests pass
  • http/swagger.yml updated (if modified Go structs or API)
  • Documentation updated or issue created (provide link to issue/pr)

@jsteenb2 jsteenb2 requested a review from a team as a code owner June 1, 2020 22:54
@jsteenb2 jsteenb2 requested review from imogenkinsman, hoorayimhelping and bthesorceror and removed request for a team June 1, 2020 22:54
@jsteenb2 jsteenb2 force-pushed the 18271/pkger_export_by_stack branch 2 times, most recently from 495753d to f978845 Compare June 1, 2020 23:23
@jsteenb2 jsteenb2 requested a review from a team as a code owner June 1, 2020 23:23
@jsteenb2 jsteenb2 removed the request for review from a team June 1, 2020 23:24
@jsteenb2 jsteenb2 force-pushed the 18271/pkger_export_by_stack branch 2 times, most recently from 8f4af33 to be930a4 Compare June 1, 2020 23:56
this ability exports all resources associated with a stack by the same
metadata.name fields as the original application had done it. This can
be used as a means to snapshot the current state of the stack. This can
be used for source control or other means.

closes: #18271
@jsteenb2 jsteenb2 force-pushed the 18271/pkger_export_by_stack branch 2 times, most recently from 128293b to 8026c22 Compare June 2, 2020 00:20
@jsteenb2 jsteenb2 force-pushed the 18271/pkger_export_by_stack branch from 8026c22 to cd2bbb1 Compare June 2, 2020 00:30
continue
}
if err != nil {
return nil, ierrors.Wrap(err, fmt.Sprintf("failed to find bucket[%s]", res.ID.String()))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so this failure message will say:

failed to find bucket[12345876]

or is [%s] some special notation?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you nailed it. The error message isn't great. I want to go through this service and update the error messages as part of our templates work. For some reason that use case feels like a good time to fixup error messaging... they platform errors we return could dramatically improve across teh platform, we can start with pkger here to try and touch that up 👍

@jsteenb2 jsteenb2 merged commit 4838a94 into master Jun 2, 2020
@jsteenb2 jsteenb2 deleted the 18271/pkger_export_by_stack branch June 2, 2020 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Export by stack
2 participants