본문 바로가기

VMware/운영(TAS)

[Tanzu 운영] (5) buildpack create 및 rename

[Tanzu 운영] (5) buildpack create 및 rename

buildpack은 TAS 설치 시 upgrade 자동 된다.

 

하지만 custom  하게 사용하는 경우나 기존에 사용하던 buildpack 버전을 추가하려 할때 

다음과 같은 방법으로 실행한다.

 

# cf login
# cf login -a https://api.sys.lui.monster -u admin -p R3lEdhKAnF-qMHvaVgxKdWwawV7BNSKs —skip-ssl-validation
# cf buildpacks

ubuntu@ip-10-0-0-238:~$ cf buildpacks
Getting buildpacks as admin...

position   name                     stack           enabled   locked   filename
1          staticfile_buildpack     cflinuxfs3      true      false    staticfile_buildpack-cached-cflinuxfs3-v1.5.28.zip
2          java_buildpack_offline   cflinuxfs3      true      false    java-buildpack-offline-cflinuxfs3-v4.48.zip
3          ruby_buildpack           cflinuxfs3      true      false    ruby_buildpack-cached-cflinuxfs3-v1.8.50.zip
4          nginx_buildpack          cflinuxfs3      true      false    nginx_buildpack-cached-cflinuxfs3-v1.1.34.zip
5          nodejs_buildpack         cflinuxfs3      true      false    nodejs_buildpack-cached-cflinuxfs3-v1.7.66.zip
6          go_buildpack             cflinuxfs3      true      false    go_buildpack-cached-cflinuxfs3-v1.9.38.zip
7          r_buildpack              cflinuxfs3      true      false    r_buildpack-cached-cflinuxfs3-v1.1.25.zip
8          python_buildpack         cflinuxfs3      true      false    python_buildpack-cached-cflinuxfs3-v1.7.49.zip
9          php_buildpack            cflinuxfs3      true      false    php_buildpack-cached-cflinuxfs3-v4.4.55.zip
10         dotnet_core_buildpack    cflinuxfs3      true      false    dotnet-core_buildpack-cached-cflinuxfs3-v2.3.38.zip
11         binary_buildpack         cflinuxfs3      true      false    binary_buildpack-cached-cflinuxfs3-v1.0.42.zip
12         binary_buildpack         windows2012R2   true      false    binary_buildpack-cached-windows2012R2-v1.0.36.zip
13         binary_buildpack         windows2016     true      false    binary_buildpack-cached-windows2016-v1.0.42.zip
14         binary_buildpack         windows         true      false    binary_buildpack-cached-windows-v1.0.42.zip
15         oracle_java_buildpack                    true      false    java-buildpack-offline-4a6a4c03.zip

 

1. 빌드팩  create

USAGE:

   cf create-buildpack BUILDPACK PATH POSITION [--disable]

# cf create-buildpack java-buildpack-48 java-buildpack-v4.48.3.zip 3

 

2. 빌드팩 rename


USAGE:

   cf update-buildpack BUILDPACK [-p PATH | -s STACK | --assign-stack NEW_STACK] [-i POSITION] [--rename NEW_NAME] [--enable|--disable] [--lock|--unlock]

 

# cf update-buildpack java-buildpack-48 --rename java-buildpack-49

 

3. 빌드팩 delete

 

USAGE:

   cf delete-buildpack BUILDPACK [-f] [-s STACK]

ubuntu@ip-10-0-0-238:~$ cf delete-buildpack binary_buildpack -s windows2012R2

Really delete the buildpack binary_buildpack? [yN]: y
Deleting buildpack binary_buildpack with stack windows2012R2...
OK