可以从脚本中的管道中访问无安全变量

Question

我正在尝试使用基本64的技术，将.ENV文件编码为管道无担保变量，如以下位置所述，但是创建的文件是空的：

我如何在bitbucket管道上运行一个env变量？

如何将变量传递给recredentials.json

image: node:16
definitions:

  caches:
    yarncustom: /usr/local/share/.cache/yarn
  steps:
    - step: &Build-step
        name: Build
        caches:
          - node
          - yarncustom
        script:
          - echo $ENV_FILE | base64 -d > .env.local
          - cat .env.local
          - yarn install
          - yarn build
        artifacts:
          - .next/**
          - node_modules/**
          - .env.local
    - step: &Deploy-step
        name: Deploy
        script:
          - pipe: atlassian/rsync-deploy:0.4.3
            variables:
              USER: $USER
              SERVER: $SERVER
              REMOTE_PATH: $REMOTE_PATH
              LOCAL_PATH: '.'
              EXTRA_ARGS: '--exclude-from=deployment-exclude-list.txt'
pipelines:
  branches:
    development:
      - step: *Build-step
      - step:
          <<: *Deploy-step
          deployment: test

。哪个有效，这意味着该变量根本不存在，尽管我读过的所有内容都表明这应该有效。

echo randomBase64String | base64 -d > .env.local

Bitbucket PiPLELINES的屏幕截图证明它存在并且不受约束：

​

Answer 1

您没有将正确的部署传递给build step。

从屏幕截图上可以看出，env_file变量在test部署中定义，因此您需要将管道更改为：

pipelines:
  branches:
    development:
      - step:
          <<: *Build-step
          deployment: Test # This is required to fix your problem
      - step:
          <<: *Deploy-step
          deployment: Other-Deployment # Don't attempt to use Test deployment twice as it's not allowed.

Answer 2

我发现您无法在步骤之间访问部署变量。但是您可以在任何步骤中访问存储库级变量。因此，我创建了一个新的步骤，以获取回购级别变量，并将其保存为以后步骤的人工制品。如果有人对此有任何改进，我很想听听！

image: node:16
definitions:

  caches:
    yarncustom: /usr/local/share/.cache/yarn
  steps:
    - step: &Dev-step
        name: Env
        script:
          - echo $DEV_ENV | base64 -di > .env.local
        artifacts:
          - .env.local
    - step: &Build-step
        name: Build
        caches:
          - node
          - yarncustom
        script:
          - yarn install
          - yarn build
        artifacts:
          - .next/**
          - node_modules/**
    - step: &Deploy-step
        name: Deploy
        script:
          - pipe: atlassian/rsync-deploy:0.4.3
            variables:
              USER: $USER
              SERVER: $SERVER
              REMOTE_PATH: $REMOTE_PATH
              LOCAL_PATH: '.'
              EXTRA_ARGS: '--exclude-from=deployment-exclude-list.txt'
pipelines:
  branches:
    development:
      - step:
          <<: *Dev-step
      - step:
          <<: *Build-step
      - step:
          <<: *Deploy-step
          deployment: test