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

RFC 66: StackSets Support (self-managed) #347

Closed
wants to merge 1 commit into from

Conversation

linsona
Copy link

@linsona linsona commented Jul 1, 2021


By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache-2.0 license

@eladb eladb changed the title RFC 332: Self Managed Stack Set Support RFC 332: StackSets Support (self-managed) Jul 7, 2021
@eladb eladb changed the title RFC 332: StackSets Support (self-managed) RFC 66: StackSets Support (self-managed) Jul 7, 2021
@eladb
Copy link
Contributor

eladb commented Jul 7, 2021

Hi @linsona thanks for creating this RFC. As @skinny85 might have mentioned, we have just revised our RFC process and we would like for you to follow the new process as described here.

Please make sure to follow process (see the checklist in #66) and update your RFC document to the new template.

I've also deduplicated the issue and we are now tracking StackSet support in #66 (totally okay if we don't support all of it from day 1).

@linsona linsona force-pushed the rfc-332 branch 2 times, most recently from 8f1460f to b5cf452 Compare July 8, 2021 18:49
@linsona
Copy link
Author

linsona commented Jul 8, 2021

I think I accidentally closed this PR when I renamed the branch, reopened new:
#357

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.

None yet

2 participants