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

cloudformation_export.html.markdown lacks explaintion of 'name' #5872

Closed
neilhwatson opened this issue Sep 13, 2018 · 1 comment · Fixed by #6060
Closed

cloudformation_export.html.markdown lacks explaintion of 'name' #5872

neilhwatson opened this issue Sep 13, 2018 · 1 comment · Fixed by #6060
Labels
documentation Introduces or discusses updates to documentation. service/cloudformation Issues and PRs that pertain to the cloudformation service.
Milestone

Comments

@neilhwatson
Copy link

neilhwatson commented Sep 13, 2018

The current documentation file cloudformation_export.html.markdown does not explain the name attribute. It appears it might be a three part name one:two:three, but the example is too arbitrary and the detailed explanation is missing.

@bflad bflad added documentation Introduces or discusses updates to documentation. service/cloudformation Issues and PRs that pertain to the cloudformation service. labels Sep 13, 2018
@bflad bflad added this to the v1.40.0 milestone Oct 4, 2018
@ghost
Copy link

ghost commented Apr 3, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@hashicorp hashicorp locked and limited conversation to collaborators Apr 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Introduces or discusses updates to documentation. service/cloudformation Issues and PRs that pertain to the cloudformation service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants