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
Cloud Template folder name is used when validating if the record exists on the server, but the name in the details.json is used when creating/updating
#210
Open
Michaelpalacce opened this issue
Jan 4, 2024
· 5 comments
Perhaps we can think of a structure where only one or the other is used as a source of truth. A good option would be to only use the folder name and add it to the details.json.
It would be beneficial if we take a similar approach to other resources to unify the logic as much as possible?
Alternatives
An alternative solution would be to use the details.json, however that will conflict with how the resources are exported.
Additional Context
N/A
The text was updated successfully, but these errors were encountered:
We can submit a bugfix to use the information in the details.json exclusively, as well as add a quick check if the 2 are the same and fail if the details.json and the folder name are not the same.
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
Description
Perhaps we can think of a structure where only one or the other is used as a source of truth. A good option would be to only use the folder name and add it to the details.json.
It would be beneficial if we take a similar approach to other resources to unify the logic as much as possible?
Alternatives
An alternative solution would be to use the details.json, however that will conflict with how the resources are exported.
Additional Context
N/A
The text was updated successfully, but these errors were encountered: