-
Suggestion
-
Resolution: Unresolved
Currently, any change to the baseUrl of a remote in a forge app's manifest will result in a major version change. Also, baseUrl in remotes currently doesn't support wildcards.
Please add the following options:
- Allow wildcards in baseUrl
- In the case where the new baseUrl reduces the scope of the original baseUrl, it may be more sensible for this to result in a minor version change instead.
For example:
Changing from:
remotes: - key: example baseUrl: "*.domain.com"
to:
remotes: - key: example baseUrl: "*.a-different-domain.com"
should result in a major version change.
On the other hand, changing from:
remotes: - key: example baseUrl: "*.domain.com"
to:
remotes: - key: example baseUrl: "subdomain.domain.com"
could be considered a minor version change.
- is related to
-
ECO-328 Allow wildcard prefix when defining baseUrls in Forge remotes
- Gathering Interest