SFDX: Variables in Source Files - Ideas - Salesforce Trailblazer Community
Trailblazer Community

All Ideas

Idea Details

Post an Idea
230  Points
Open
Idea has been posted. Give it an upvote or downvote.

SFDX: Variables in Source Files

Developer Tools

Along the lines of this question: https://success.salesforce.com/0D53A00004oPi5M

It would be great if we could include variables within the Source files which could be replaced before push and ignored during pull.

Our particular app contains several Custom Metadata components and a Named Credential which would largely benefit from being able to use local environment variables and keep any risk of hard-coded creds getting into source control.
 
<CustomMetadata ...>
    <label>Global Settings</label>
    <protected>false</protected>
 ...
    <values>
        <field>Session_Token__c</field>
        <value xsi:type="xsd:string">${SessionToken}</value>
    </values>
</CustomMetadata>
or
<NamedCredential xmlns="http://soap.sforce.com/2006/04/metadata">
    <allowMergeFieldsInBody>false</allowMergeFieldsInBody>
    <allowMergeFieldsInHeader>false</allowMergeFieldsInHeader>
    <awsAccessKey>${AWS_ACCESS_KEY}</awsAccessKey>
    <awsSecretAccessKey>${AWS_SECRET_KEY}</awsSecretAccessKey>
    <awsRegion>us-east-1</awsRegion>
    <awsService>execute-api</awsService>
    <endpoint>https://api.example.com/</endpoint>
    <generateAuthorizationHeader>true</generateAuthorizationHeader>
    <label>Example API</label>
    <principalType>NamedUser</principalType>
    <protocol>AwsSv4</protocol>
</NamedCredential>

Merge Idea · Flag

  • Upvotes
  • Downvotes

Ideas

Apps

from AppExchange

Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.



 

 

Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.

Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.


 

Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.