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

Export by stack #18271

Closed
3 tasks
jsteenb2 opened this issue May 28, 2020 · 0 comments · Fixed by #18322
Closed
3 tasks

Export by stack #18271

jsteenb2 opened this issue May 28, 2020 · 0 comments · Fixed by #18322
Assignees
Labels
area/templates influxdb templates and pkger related issues team/user-tools

Comments

@jsteenb2
Copy link
Contributor

jsteenb2 commented May 28, 2020

As a user,
I want to to export my existing stack in the form of a template,
so that I can update/patch my package in a controlled manner

AC

  • 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
@jsteenb2 jsteenb2 added area/templates influxdb templates and pkger related issues team/user-tools labels May 28, 2020
@jsteenb2 jsteenb2 self-assigned this May 28, 2020
jsteenb2 added a commit that referenced this issue 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
jsteenb2 added a commit that referenced this issue 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
jsteenb2 added a commit that referenced this issue 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
jsteenb2 added a commit that referenced this issue 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
jsteenb2 added a commit that referenced this issue 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
jsteenb2 added a commit that referenced this issue 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
jsteenb2 added a commit that referenced this issue Jun 2, 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/templates influxdb templates and pkger related issues team/user-tools
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant