Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generate modules metadata #232

Merged

Conversation

bhsubra
Copy link
Contributor

@bhsubra bhsubra commented Feb 1, 2023

Changes in the PR include:

  1. Generate modules metadata that'll be used in completion scenarios
  2. I'll have a follow up PR to write the generated data to storage account container

Verified the changes in dogfood via:
bhsubra#1

@bhsubra bhsubra requested a review from a team as a code owner February 1, 2023 21:00
@ghost
Copy link

ghost commented Feb 1, 2023

This PR contains changes to the CI definitions. Reviews from @Azure/bicep-admins are needed.

@bhsubra bhsubra marked this pull request as draft February 1, 2023 21:00
@bhsubra bhsubra changed the title Write modules metadata to storage account container Generate modules metadata Feb 1, 2023
@bhsubra bhsubra marked this pull request as ready for review February 1, 2023 21:13
@@ -0,0 +1,40 @@
async function getModulesMetadata({ require, core }) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mind adding a JSDoc comment to annotate the types of parameters?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, updated here:
20d412d

Thanks!

* @param {string} dir
*/
function getSubdirNames(dir) {
const fs = require("fs");
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should fs remain a parameter and be passed from the caller?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated here:
20d412d

Thanks!

@bhsubra bhsubra requested a review from shenglol February 1, 2023 22:30
Comment on lines +3 to +16
workflow_call:
secrets:
# Secrets must be passed from the caller workflow explicitly.
CLIENT_ID:
required: true
TENANT_ID:
required: true
SUBSCRIPTION_ID:
required: true
workflow_dispatch:

permissions:
id-token: write
contents: read
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are the secrets needed? If not, we should remove them.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I'll be sending out a follow up PR to login to azure and write the modules metadata to storage account container. Let me know if you want me to remove it here and include it in other PR.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, in that case we can leave them as is.

@bhsubra bhsubra requested a review from shenglol February 1, 2023 22:57
@bhsubra bhsubra merged commit 33a678d into main Feb 1, 2023
@bhsubra bhsubra deleted the dev/bhsubra/WriteModulesMetadataToStorageAccountContainer branch February 1, 2023 23:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants