You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some cases, such as SQL Database with {{instance}}:{{name}} form, we support import formats with non-standard delimiters. We should remove them as part of 3.0.0 to ensure consistency across resources and to simplify MM generation.
If it's impossible to remove in some cases - say, if / is an ambiguous character - we should instead add support for different delimiters to MM.
The text was updated successfully, but these errors were encountered:
I don't think so! I definitely changed a couple of them that used : or ., but I didn't change ones where a self link wouldn't be helpful or applicable, like organization policies
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. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
Mar 28, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In some cases, such as SQL Database with
{{instance}}:{{name}}
form, we support import formats with non-standard delimiters. We should remove them as part of3.0.0
to ensure consistency across resources and to simplify MM generation.If it's impossible to remove in some cases - say, if
/
is an ambiguous character - we should instead add support for different delimiters to MM.The text was updated successfully, but these errors were encountered: