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
It would be nice if I had access to variables for timestamp, space-id, source-environment-id and target-environment-id inside merge export --output-file so I dont have to query all that data myself when I want to save my generated migrations to a different path. I'm thinking of something that date libraries usually do where you can use something like %d. %m. %Y and these variables get replaced by the corresponding data.
Actual Behavior
I can either use the default path and file name or need to specify a full path. When I would want to add the space Id to the file name, I would get it beforehand.
Possible Solution
see expected behavior
Context
I'm trying to build a migration script for ci/cd-pipeline. We have multiple spaces and environments. As there is no information written about those inside the migration file, I would like to extract that from the file name.
The text was updated successfully, but these errors were encountered:
Expected Behavior
It would be nice if I had access to variables for
timestamp
,space-id
,source-environment-id
andtarget-environment-id
insidemerge export --output-file
so I dont have to query all that data myself when I want to save my generated migrations to a different path. I'm thinking of something that date libraries usually do where you can use something like%d. %m. %Y
and these variables get replaced by the corresponding data.Actual Behavior
I can either use the default path and file name or need to specify a full path. When I would want to add the space Id to the file name, I would get it beforehand.
Possible Solution
see expected behavior
Context
I'm trying to build a migration script for ci/cd-pipeline. We have multiple spaces and environments. As there is no information written about those inside the migration file, I would like to extract that from the file name.
The text was updated successfully, but these errors were encountered: