Enable use of multiple manifests

[mmitche]

When there are multiple source-build platforms, the manifest files will end up the same name (typically) unless set explicitly.

To double check:

• The right tests are in and and the right validation has happened. Guidance: https://github.com/dotnet/arcade/tree/main/Documentation/Validation

[mmitche]

@crummel and @MichaelSimons We need to have different asset manifest file names, but I'm torn on this approach:

Pros:

• Aligns with what repos do when they have multiple legs that may have overlap in nams

Cons:

• Maybe should go somewhere in the props/targets files in arcade? But, I wasn't able to find a set of target properties that would be generally useable for generating the manifest file name...so maybe this is better?

[mmitche]

@crummel@MichaelSimons If you get a chance this week, comments on this would be much appreciated. This should unblock the rid agnostic leg in runtime,

[mmitche]

When there are multiple source-build platforms, the manifest files will end up the same name (typically) unless set explicitly.

To double check:

• The right tests are in and and the right validation has happened. Guidance: https://github.com/dotnet/arcade/tree/main/Documentation/Validation

[mmitche]

@crummel and @MichaelSimons We need to have different asset manifest file names, but I'm torn on this approach:

Pros:

• Aligns with what repos do when they have multiple legs that may have overlap in nams

Cons:

• Maybe should go somewhere in the props/targets files in arcade? But, I wasn't able to find a set of target properties that would be generally useable for generating the manifest file name...so maybe this is better?

[mmitche]

@crummel@MichaelSimons If you get a chance this week, comments on this would be much appreciated. This should unblock the rid agnostic leg in runtime,

[mmitche]

When there are multiple source-build platforms, the manifest files will end up the same name (typically) unless set explicitly.

To double check:

• The right tests are in and and the right validation has happened. Guidance: https://github.com/dotnet/arcade/tree/main/Documentation/Validation

[mmitche]

@crummel and @MichaelSimons We need to have different asset manifest file names, but I'm torn on this approach:

Pros:

• Aligns with what repos do when they have multiple legs that may have overlap in nams

Cons:

• Maybe should go somewhere in the props/targets files in arcade? But, I wasn't able to find a set of target properties that would be generally useable for generating the manifest file name...so maybe this is better?

[mmitche]

@crummel@MichaelSimons If you get a chance this week, comments on this would be much appreciated. This should unblock the rid agnostic leg in runtime,

[mmitche]

When there are multiple source-build platforms, the manifest files will end up the same name (typically) unless set explicitly.

To double check:

• The right tests are in and and the right validation has happened. Guidance: https://github.com/dotnet/arcade/tree/main/Documentation/Validation

[mmitche]

@crummel and @MichaelSimons We need to have different asset manifest file names, but I'm torn on this approach:

Pros:

• Aligns with what repos do when they have multiple legs that may have overlap in nams

Cons:

• Maybe should go somewhere in the props/targets files in arcade? But, I wasn't able to find a set of target properties that would be generally useable for generating the manifest file name...so maybe this is better?

[mmitche]

@crummel@MichaelSimons If you get a chance this week, comments on this would be much appreciated. This should unblock the rid agnostic leg in runtime,

[mmitche]

When there are multiple source-build platforms, the manifest files will end up the same name (typically) unless set explicitly.

To double check:

• The right tests are in and and the right validation has happened. Guidance: https://github.com/dotnet/arcade/tree/main/Documentation/Validation

[mmitche]

@crummel and @MichaelSimons We need to have different asset manifest file names, but I'm torn on this approach:

Pros:

• Aligns with what repos do when they have multiple legs that may have overlap in nams

Cons:

• Maybe should go somewhere in the props/targets files in arcade? But, I wasn't able to find a set of target properties that would be generally useable for generating the manifest file name...so maybe this is better?

[mmitche]

@crummel@MichaelSimons If you get a chance this week, comments on this would be much appreciated. This should unblock the rid agnostic leg in runtime,

[mmitche]

When there are multiple source-build platforms, the manifest files will end up the same name (typically) unless set explicitly.

To double check:

• The right tests are in and and the right validation has happened. Guidance: https://github.com/dotnet/arcade/tree/main/Documentation/Validation

[mmitche]

@crummel and @MichaelSimons We need to have different asset manifest file names, but I'm torn on this approach:

Pros:

• Aligns with what repos do when they have multiple legs that may have overlap in nams

Cons:

• Maybe should go somewhere in the props/targets files in arcade? But, I wasn't able to find a set of target properties that would be generally useable for generating the manifest file name...so maybe this is better?

[mmitche]

@crummel@MichaelSimons If you get a chance this week, comments on this would be much appreciated. This should unblock the rid agnostic leg in runtime,

[mmitche]

When there are multiple source-build platforms, the manifest files will end up the same name (typically) unless set explicitly.

To double check:

• The right tests are in and and the right validation has happened. Guidance: https://github.com/dotnet/arcade/tree/main/Documentation/Validation

[mmitche]

@crummel and @MichaelSimons We need to have different asset manifest file names, but I'm torn on this approach:

Pros:

• Aligns with what repos do when they have multiple legs that may have overlap in nams

Cons:

• Maybe should go somewhere in the props/targets files in arcade? But, I wasn't able to find a set of target properties that would be generally useable for generating the manifest file name...so maybe this is better?

[mmitche]

@crummel@MichaelSimons If you get a chance this week, comments on this would be much appreciated. This should unblock the rid agnostic leg in runtime,

[mmitche]

When there are multiple source-build platforms, the manifest files will end up the same name (typically) unless set explicitly.

To double check:

• The right tests are in and and the right validation has happened. Guidance: https://github.com/dotnet/arcade/tree/main/Documentation/Validation

[mmitche]

@crummel and @MichaelSimons We need to have different asset manifest file names, but I'm torn on this approach:

Pros:

• Aligns with what repos do when they have multiple legs that may have overlap in nams

Cons:

• Maybe should go somewhere in the props/targets files in arcade? But, I wasn't able to find a set of target properties that would be generally useable for generating the manifest file name...so maybe this is better?

[mmitche]

@crummel@MichaelSimons If you get a chance this week, comments on this would be much appreciated. This should unblock the rid agnostic leg in runtime,