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
Hello @scottdevelop1, and thank you for spkl. I'll create a PR if you approve my suggestion. Suggestion is the following:
"overwrite" flag should be honored when publishing web resources by forcing content update and adding resource to solution even if resource has no changes.
Use case: there is a "default" solution is spkl.json for publishing web resources, aka "WebResources". It is useful when new resource is created and published at the first time to make sure that it will be created with correct schema. Later, we create new "release solution" to cherry-pick changes we want to ship with release. If I locally change spkl.json to publish to this new solution and than publish web resources again, new resource will not be included as it might have no changes. As the result it can be accidentally not published to next environment.
The text was updated successfully, but these errors were encountered:
Hello @scottdevelop1, and thank you for spkl. I'll create a PR if you approve my suggestion. Suggestion is the following:
Use case: there is a "default" solution is spkl.json for publishing web resources, aka "WebResources". It is useful when new resource is created and published at the first time to make sure that it will be created with correct schema. Later, we create new "release solution" to cherry-pick changes we want to ship with release. If I locally change spkl.json to publish to this new solution and than publish web resources again, new resource will not be included as it might have no changes. As the result it can be accidentally not published to next environment.
The text was updated successfully, but these errors were encountered: