[CustomScript] extension should allow for a script payload
See original GitHub issueGiven that uploading dependencies to an added storage account may be unfeasible (or just too much overhead) when using CLI scripting, this extension should support the use case of inlining a shell script as part of an ARM template - something like the example below would go a very long way towards matching this competing feature and allowing for easy migration.
"settings": {
"inlineScript": "#!/bin/bash\nsudo apt-get -y update\nsudo apt-get install nginx"
}
Issue Analytics
- State:
- Created 7 years ago
- Comments:24 (21 by maintainers)
Top Results From Across the Web
Run Custom Script Extension on Linux VMs in Azure
The Custom Script Extension integrates with Azure Resource Manager templates. You can also run it by using the Azure CLI, PowerShell, ...
Read more >Azure Custom Script Extension. Execute script as another user
Yes, Azure Custom Script Extension runs as the System account . This means using the Azure VM Custom Script Extension we can run...
Read more >Registering custom script includes against ... - ServiceNow Docs
Register custom script includes against a selected scripted extension point in the application code.
Read more >Resource Scripts | Metasploit Documentation - Docs @ Rapid7
Resource scripts enable you to do almost anything you can do in the Metasploit ... through the framework, you may want to build...
Read more >Scripting in Postman
This allows you to write API tests, build requests that can contain ... For every request in a collection, scripts will execute in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@rcarmo your template will probably fail with error:
@rcarmo I was wrong about my earlier statement saying
customData
does accept non-base64 strings as well. It only accepts base64 strings and the docs are correct.If you care about readability in your ARM templates you can specify a
myScript
in"variables"
or"parameters"
section and incustomData
field you can use:so it essentially is the same thing as if customData accepted non-base64 strings.