Azure/functions-action

Additional deployment infos in azure portal

nikolaiessel opened this issue · 3 comments

We just migrate projects from DevOps to Github.
When we use this action to deploy our functions, we loosing source informations comparing with DevOps release pipeline.

The reason is, that the _getUpdateHistoryRequest supports custom message content, but callees only deliver a slotName

private _getUpdateHistoryRequest(isDeploymentSuccess: boolean, deploymentID?: string, customMessage?: any): any {
deploymentID = !!deploymentID ? deploymentID : this.getDeploymentID();
var message: {[index: string]:any} = {
type : "deployment",
sha : `${process.env.GITHUB_SHA}`,
repoName : `${process.env.GITHUB_REPOSITORY}`,
actor: `${process.env.GITHUB_ACTOR}`
};
if(!!customMessage) {
// Append Custom Messages to original message
for(var attribute in customMessage) {
message[attribute] = customMessage[attribute];
}
}

The message JSON of this Action is

{
  "type": "deployment",
  "sha": "...",
  "repoName": "...",
  "actor": "...",
  "slotName": "production"
}

DevOps creates

{
  "type": "deployment",
  "commitId": "...",
  "buildId": "...",
  "releaseId": "...",
  "buildNumber": "...",
  "releaseName": "...",
  "repoProvider": "TfsGit",
  "repoName": "...",
  "collectionUrl": "https://dev.azure.com/...",
  "teamProject": "...",
  "buildProjectUrl": "https://dev.azure.com/...",
  "repositoryUrl": "",
  "branch": "main",
  "teamProjectName": "...",
  "slotName": "production"
}

Maybe the azure portal will display the informations too, if GitHub Action delivers it

This issue is idle because it has been open for 14 days with no activity.

yeah, idle because no maintainer had time to look into it. All that "bots" aren´t "user-friendly" (in all issue-tracking systems)

This issue is idle because it has been open for 14 days with no activity.