[hippi345]

Description

After inletsctl create on Azure, the printed inletsctl delete example left out --subscription-id, so copy-pasting it failed with InvalidSubscriptionId unless the flag was added by hand. The sample now includes --subscription-id when it's set with the flag or present in the Azure credentials JSON (subscriptionId). Both the HTTPS and TCP summaries use the new helper.

Closes #117

How Has This Been Tested?

• make gofmt
• make test
• make all

Added unit tests for subscriptionIDFromAzureAuth and sampleDeleteCommand.

How are existing users impacted? What migration steps/scripts do we need?

No breaking changes. Other providers see the same delete line as before. Azure users get a complete delete command when a subscription ID is available.

Checklist:

I have:

• updated the documentation and/or roadmap (if required)
• read the CONTRIBUTION guide
• signed-off my commits with git commit -s
• added unit tests

[derek]

Thank you for your contribution. It seems that one or more of your commits have a "Signed-off-by" statement with an anonymous email address. The Developer Certificate of Origin (DCO) requires all commits to be signed off by genuine, contactable individuals. Please see our contributing guide.

### :bulb: Shall we fix this?

This will only take a few moments.

First, clone your fork and checkout this branch using the git CLI.

Next, set up your real name and email address:

git config --global user.name "Your Full Name"
git config --global user.email "you@domain.com"

Finally, run one of these commands to add the "Signed-off-by" line to your commits.

If you only have one commit so far then run: git commit --amend --signoff and then git push --force.
If you have multiple commits, watch this video.

Check that the message has been added properly by running "git log".