@jhuleatt this would be a very useful feature.

I currently have a Firebase Project (my-project) with Hosting configured for 2 sites (my-site-1, my-site-2).
When I build and deploy my-project on the command line I run this

firebase deploy --only hosting:my-target-1 --project my-project

My .firebaserc is like this:

{
  "projects": {
    "default": "my-project"
  },
  "targets": {
    "my-project": {
      "hosting": {
        "my-target-1": [
          "my-site-1"
        ],
        "my-target-2": [
          "my-site-2"
        ]
      }
    }
  }
}

I can imagine having a target property on the with property under uses such as

      - uses: FirebaseExtended/action-hosting-deploy@v0
        with:
          repoToken: "${{ secrets.GITHUB_TOKEN }}"
          firebaseServiceAccount: "${{ secrets.FIREBASE_SERVICE_ACCOUNT }}"
          channelId: live
          target: my-target-1

I'd be happy to help with this feature, but still studying your code. I see a potential place to hook in on L21

action-hosting-deploy/src/deploy.ts

Lines 19 to 24 in 79d1e17

    
           export type SiteDeploy = { 
        
             site: string; 
        
             target: string | undefined; 
        
             url: string; 
        
             expireTime: string; 
        
           };

but not yet sure how to thread that through. Will keep investigating.

	export type SiteDeploy = {
	site: string;
	target: string \| undefined;
	url: string;
	expireTime: string;
	};

Possible to support specific deploy targets? #6

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions