Puppet Enterprise 2019.3.0 6.12.0 (64-bit) 軟體資訊介紹&下載

Avocode (64-bit),軟體教學,軟體下載,電腦問題,電腦教學
打開 PSD& 使用 Avocode 64 位在 Windows PC 上進行草圖設計。生成 CSS,Swift& XML 直接從圖層中導出圖像,顏色,字體,樣式,大小和尺寸。邀請您的團隊成員,輕鬆管理用戶權限。任何數量的人都可以同時檢查相同的設計。通過評論給出精確的設計反饋,並在發生變化時得到通知。將設計修訂保持在一起並組織到項目中。將任何 Photoshop 和 Sketch 源文件上傳到一個安全的地方,整個團隊都可以訪問,打開並全天候下載。免費為 Windows PC 64 位下載 Avocode

Avocode 功能:

打開.psd& .sketch without Photoshop& Sketch
Avocode 自己渲染 Photoshop 和 Sketch 設計。因此,您可以打開並檢查您上傳到 Avocode 的任何設計。在任何操作系統上,無需設計人員的工具.

導出 CSS,Swift,Android& React 從 design
生成簡潔的 CSS,Less,Sass,Less,SCSS,手寫筆,Swift,Android,& JS 代碼中的 CSS,包括圖層和字體樣式,px,pt 和 dp 中的單位以及 HEX,UIcolor 或 HEX8 中的顏色,最大為 @ 4x 或 xxxhdpi 分辨率
選擇一個圖層,多個圖層或設計的一個切片並將其導出作為圖像。為各種分辨率添加更多的變體。你甚至可以升級和導出矢量形狀,以適應任何桌面,iOS 或 Android 屏幕.

Handpicked#BADA55 colors
手動複製顏色和轉換它們... 這是昨天。只需選擇一種顏色,顏色代碼將立即添加到您的剪貼板中,因此您可以將其粘貼到需要的位置.

將文本圖層導出為純文本,圖像或 html 代碼 6122 8688 當您選擇文本圖層時,可以將其導出為圖像,複製純文本或複制 HTML 標籤的文本。 STYLES 面板將顯示您的所有內容,如 font-family,font-weight 和 font-size.

精確的測量,不會造成眼球的損壞
即時抓取任何尺寸或距離。添加,移動和刪除指南,讓您檢查精確對齊。您也可以使用它們來測量從任何物體到任何地方的距離。

定義所有變量為
您可以通過隱藏和重新排序其部分來自定義代碼輸出。定義並替換代碼中的任何值(顏色,字體,漸變,大小,距離)作為變量,並自動出現在導出的代碼中.

分享設計並邀請團隊成員
讓您的開發人員在 Avocode 中自行提取所有設計規格。您可以邀請需要檢查設計的團隊成員,也可以與僅需要評論的人員共享公共鏈接。通過插件

Sync .psd 和.sketch 您可以從字面上留在 Photoshop 或 Sketch 應用程序上傳設計或修訂到 Avocode。安裝我們的插件,點擊同步,設計將突然出現在您的 Avocode 雲中.

選擇設計的任何區域並在其上面評論
討論所有事情,解釋您的想法,並通過設計頂部的評論留給您的同事反饋。突出顯示任何區域,實時添加,回復和解決與您的團隊的意見.

通過 Slack 通知您的團隊的進展情況
當您的團隊配對,上傳設計,添加修訂版本時,通過電子郵件或專用 Slack 渠道通知您,或寫評論。您還可以跟踪 Avocode 應用程序中的活動欄的進度.

管理誰看到什麼
邀請團隊成員,自由職業者和承包商,並管理他們對團隊中特定項目的權限。通過公共鏈接向第三方(如客戶)分享設計預覽,並讓他們發表評論.

一個地方適合您的所有設計
將設計上傳到 Avocode 雲,與您的團隊同步版本和設計設置(規模,平台,單位) 。讓您的團隊成員盡可能多地訪問,檢查和下載最新的設計修訂版本 24 / 7.

您願景中的所有修訂版本
Re-design。 Avocode 作為所有設計版本的最新版本庫。您可以簡單地將修訂彼此堆疊起來,然後以可視方式並排比較它們.

零時間安全保持安全,而且非常安全
第二次將您的設計上載到 Avocode 雲,您的團隊就可以訪問了。您在 Avocode 上傳的所有內容都使用 SSL 證書進行加密,因此您的設計將保持您的真實身份.

在您的項目中設計和搜索設計和搜索
Avocode 可以讓您在多個項目中工作

Avocode (64-bit) Screenshot 1
Avocode (64-bit) Screenshot 2
Avocode (64-bit) Screenshot 3

Puppet Enterprise 2019.3.0 6.12.0 (64-bit)

puppet-agent-6.12.0-x64.msi

35.7 MB

Windows 7 64 / Windows 8 64 / Windows 10 64

未分類

Avocode, Inc.

https://avocode.com/

2020-01-31

What's new in this version:

Enhancements:
- Puppet ensures platform repositories aren't installed in order to prevent accidental agent upgrade
- Previously, Bolt users who installed the Puppet 5 or 6 platform repositories could experience unsupported agent upgrades on managed nodes. With this release, Puppet ensures that the release packages for those platforms are not installed on managed nodes by enforcing ensure => 'absent' for the packages.
- Windows install script optionally downloads a tarball of plug-ins
- For Windows agents, the agent install script optionally downloads a tarball of plug-ins from the master before the agent runs for the first time. Depending on how many modules you have installed, bulk plug-in sync can speed agent installation significantly.
- Note: If your master runs in a different environment from your agent nodes, you might see some reduced benefit from bulk plug-in sync. The plug-in tarball is created based on the plug-ins running on the master agent, which might not match the plug-ins required for agents in a different environment.
- This feature is controlled by the setting pe_repo::enable_windows_bulk_pluginsync which you can configure in Hiera or in the console. The default setting for bulk plug-in sync is false (disabled).
- puppet infrastructure run commands no longer require an authentication token
- puppet infrastructure run commands that affect PuppetDB, including migrate_split_to_mono, convert_legacy_compiler, and enable_ha_failover, no longer require setting up token-based authentication as a prerequisite for running the command. By default, these commands use the master's PuppetDB certificate for authentication.
- puppet infrastructure run commands provide more useful output
- puppet infrastructure run commands, such as those for regenerating certificates or enabling high availability failover, provide more readable output, making them easier to troubleshoot.
- Calculations for PostgreSQL settings are fine-tuned
- The shared_buffers setting uses less RAM by default due to improvements in calculating PostgreSQL settings. Previously, PostgreSQL settings were based on the total RAM allocated to the node it was installed on. Settings are now calculated based on total RAM less the default RAM used by PE services. As a result, on an 8GB installation for example, the default shared_buffers setting is reduced from ~2GB to ~1GB.
- PostgreSQL can optionally be cleaned up after upgrading
- After upgrading, you can optionally remove packages and directories associated with older PostgreSQL versions with the command puppet infrastructure run remove_old_postgresql_versions. If applicable, the installer prompts you to complete this cleanup.
- nix command for regenerating agent certificates includes a parameter for CRL cleanup
- The puppet infra run regenerate_agent_certificate command includes a clean_crl parameter. Setting clean_crl to true cleans up the local CRL bundle. When you regenerate certificates for *nix agents after recreating your certificate authority, you must include this parameter with the value set to true. If you're regenerating agent certificates without recreating the CA, you don't need to clean up the CRL.
- Puppet Server multithreaded setting
- There is a new Puppet Server setting for enabling a multithreaded mode, which uses a single JRuby instance to process requests, like catalog compiles, concurrently. Activate the setting by changing the puppet_enterprise::master::puppetserver::jruby_puppet_multithreaded parameter to true.
- puppetlabs-pe_bootstrap task supports Puppet agent on CentOS 8
- The puppetlabs-pe_bootstrap task that ships in PE has been updated to support Puppet agent installation on CentOS 8
- New task targets API
- Use the new task targets API to fine-tune task permissions automatically. See POST /command/task_target and Puppet orchestrator API: scopes endpoint

Console enhancements:
These are enhancements to the console in this release:
- Plan metadata
- View plan metadata and parameters. To view them in the console, type in a name of a plan in the Plan field and click View plan metadata. To view metadata on the command line, run puppet plan show <PLAN NAME>.
- Test connections option
- Test connections for nodes and devices before adding them to your inventory. This option is enabled by default on the Inventory page. If a connection fails, you can edit the node or device information and try again.
- Custom PQL queries
- Add your own custom PQL queries to the console and use them for running Puppet and tasks. See Add custom PQL queries to the console for more information.

Breadcrumbs:
- Pages in the console now have breadcrumbs, showing you where you are in the interface. The breadcrumbs are links you can use to move to parent pages.

Transport details:
- View the transport mechanism, SSH or WinRM for example, for task runs in the Connections and Activity tabs on the Nodes page.
- Run drop-down menu
- The Run Puppet on these nodes button has been replaced with a Run drop down menu so you can run Puppetor run a task for the nodes listed on the current page. The new option is available on the Overview, Events, and Packages pages.
- Task and plan environment default
- When you run a task or a plan in the console, you no longer need to specify which environment you would like to run the plan or task in if you are running in production. The console now defaults to production.
- Additional run options
- In addition to no-op, you can now specify debug, trace, and eval-trace run options when running Puppet

Platform support:
- This version adds support for these platforms

Agent:
- Fedora 31

Deprecations and removals:
- Deprecated platform support

Support for these platforms is deprecated in this release and will be removed in a future version of PE:
- Master
- Enterprise Linux 6
- Ubuntu 16.04

Razor deprecated:
- Razor, the provisioning application that deploys bare-metal systems, is deprecated in this release, and will be removed in a future version. If you can to continue using Razor, you can use the open source version of the tool, available from GitHub.

Node graph removed:
- The node graph in the console has been removed due to infrequent use. The graph was used to view relationships between resources and classes within a node catalog. To generate a node graph now, use the Puppet VS Code extension.

Resolved issues:
- puppet infrastructure run commands could fail if the agent was run with cron
- puppet infrastructure run commands, such as those used for certain installation, upgrade, and certificate management tasks, could fail if the Puppet agent was run with cron. The failure occurred if the command conflicted with a Puppet run.
- Mismatch between classifier classification and matching nodes for regexp rules
- PuppetDB’s regular expression matching had surprising behaviors for structured fact value comparisons. For example, the structured fact os is a rule that matches ["~", "os", ":"]. PuppetDB would unintentionally match every node that has the os structured fact because the regular expression was applied to the JSON encoded version of the fact value.
- The classifier does not use PuppetDB for determining classification and regular expressions in the classifier rules syntax only support direct value comparisons for string types.
- This caused issues in the console where the node list and counts for the "matching nodes" display sometimes indicated that nodes were matching even though the classifier would not consider them matching.
- Now, the same criteria is applied to the displays and counts that the classifier uses. The output of the classifier’s rule translation endpoints makes queries that match the classifier behavior.
- Note: This fix doesn't change the way nodes are classified, only how the console displays matching nodes
- Code manager could not deploy Forge modules with a proxy
- The commands puppet code deploy and r10k failed when behind a proxy. The commands didn't use the configured proxy settings and using them would result in problems downloading modules from the Puppet Forge. This was due to an issue in a dependency gem.
- Now, the commands work behind a proxy
- Orchestrator error message included Bolt command suggestions
- When a plan or task was not found, the resulting error message gave a suggestion to run bolt {plan,task} show, which is unhelpful in PE. The error message no longer shows the Bolt command suggestion.
- bolt.yaml plans did not work in PE
- Plans with bolt.yaml in the root directory of the environment will no longer fail. Don't use the modulepath setting in bolt.yaml, because it may lead to unintended consequences when loading tasks and plans.
- Ed25519 SSH keys couldn't be used to run task on agentless node
- Running a task on an agentless node using an ed25519 SSH keys would result in an error

Avocode (64-bit) 相關參考資料