feat: add ASK_SKIP_DOMAIN_VALIDATION to allow skipping manifest api v… #500
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…alidation prior to skill enablement
Issue #, if available:
Description of changes:
if attempting to deploy a skill that is anything other than custom or music the domain validation will fail and prevent skill enablement from being attempted. By setting the following env variable, the cli will ignore your manifest domain apis and attempt to enable the skill without any prior checks.
ASK_FORCE_ENABLE
example usage:
you'll see a warning show up on the terminal stating that the env variable was detected and validation was skipped
Note: You should not set this env variable, if you have a smartHome skill or any other skill types known to fail skill enablement. It will just make extra service api calls that will end up failing.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.