azartifacts preview v0.1.0

[jhendrixMSFT]

• The purpose of this PR is explained in this or a referenced issue.
• The PR does not update generated files.
  • These files are managed by the codegen framework at Azure/autorest.go.
• Tests are included and/or updated for code changes.
• Updates to CHANGELOG.md are included.
• MIT license headers are included in each file.

[check-enforcer]

This repository is protected by Check Enforcer. The check-enforcer check-run will not pass until there is at least one more check-run successfully passing. Check Enforcer supports the following comment commands:

• /check-enforcer evaluate; tells Check Enforcer to evaluate this pull request.
• /check-enforcer override; by-pass Check Enforcer (approvals still required).

[jhendrixMSFT]

/check-enforcer override

[ArcturusZhang]

Hi @jhendrixMSFT do we need to add some synapse data-plane specific information in this PR? For instance like the things added to go-autorest previously by this PR: Azure/go-autorest#552

And also, the CI pipelines are not working for synapse in this PR

[jhendrixMSFT]

CI has not yet been hooked up for this module as the yaml hasn't been committed yet.

The codegen is self-contained, so no need to add anything else. Long-term, I don't know that we'll add a similar environment table like we have in go-autorest.

[catalinaperalta]

I think this needs a README with at least the same information the ARM SDKs have....to include information like how to use the ctor for a new connection, where azidentity is, etc. I think for now it could be a copy of one of the ARM ones.

I say this in part, because I was looking at the connection file and then wondered if people would easily know that azidentity implements azcore.Credential and they wont go off making their own credential or using something else. Aside from the fact that even the simpler READMEs we have for the ARM libs provide some basic and useful info.

[jhendrixMSFT]

The README has been added.

[catalinaperalta]

LGTM

[ArcturusZhang]

We might need to capitalize the first letter here

Suggested change

	- an [Azure subscription](https://azure.microsoft.com/free/)
	- An [Azure subscription](https://azure.microsoft.com/free/)

[ArcturusZhang]

The CI is not working therefore this link is not reported as invalid. Therefore the CI pipelines are designed not to work in the first PR of a module?

[jhendrixMSFT]

We still need to figure out how this will work long-term. At present, we can assume that CI won't be hooked up for the first module release :(

[ArcturusZhang]

That would be the most unfortunate... do we have to locally run go vet to verify the SDK could compile properly?

[jhendrixMSFT]

That's what I did yes. Long term, we'll want to have an easy way to set up CI before releasing a module. I didn't bother with it here given our requirement for expedience.